Simplify upgrade reporting prompt with checkbox-based preference#5172
Simplify upgrade reporting prompt with checkbox-based preference#5172
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
Co-authored-by: netmindz <442066+netmindz@users.noreply.github.com>
Co-authored-by: netmindz <442066+netmindz@users.noreply.github.com>
|
Please change and options to [ Report this update ] |
- Replace 4-button design with 2 buttons: "Report this update" and "Skip reporting" - Add checkbox "Save my choice for future updates" (checked by default) - When checkbox is checked: - "Report this update" enables automatic reporting for future upgrades - "Skip reporting" saves "never ask" preference - When unchecked, choice applies only to current prompt Co-authored-by: netmindz <442066+netmindz@users.noreply.github.com>
Changed to the requested 2-button + checkbox design in commit d4f365e. The prompt now shows:
When the checkbox is checked, the choice is saved for future upgrades. When unchecked, the user will be prompted again next time. |
|
@copilot given the presence of the save tick box, the report button should just say "Report update" |
- Remove duplicate toast messages when checkbox is checked - Show appropriate message based on saveChoice state - Ensure error toasts are visible after overlay is removed Co-authored-by: netmindz <442066+netmindz@users.noreply.github.com>
Per feedback, simplified button text since the checkbox already provides context about saving choices for future updates. Co-authored-by: netmindz <442066+netmindz@users.noreply.github.com>
|
@coderabbitai can you check the final logic please, it doesn't look quite right |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: Length of output: 5022
When a user has opted in for automatic reporting and a future upgrade is detected, the code calls: if (versionInfo.alwaysReport) {
// Automatically report if user opted in for always reporting
reportUpgradeEvent(info, storedVersion); // ❌ Missing third parameter!
}But the function signature expects three parameters: function reportUpgradeEvent(info, oldVersion, alwaysReport) {The Problem:
The Fix: if (versionInfo.alwaysReport) {
// Automatically report if user opted in for always reporting
reportUpgradeEvent(info, storedVersion, true);
}This ensures the 🧠 Learnings used |
Please fix this @copilot |
When automatic reporting was triggered, the third parameter (alwaysReport) was missing in the reportUpgradeEvent call. This caused the preference to be lost after the first automatic report, requiring the user to be prompted again on the next upgrade. Fixed by passing 'true' as the third parameter to maintain the user's preference for all future automatic reports. Co-authored-by: netmindz <442066+netmindz@users.noreply.github.com>
Fixed in commit 354da8f. The automatic reporting call was missing the third parameter, causing the |
|
Please confirm the following behaviour Report, without save - report and ask questions on next update |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: Length of output: 5231 🏁 Script executed: Length of output: 0 🏁 Script executed: Length of output: 82 🏁 Script executed: Length of output: 1508 🏁 Script executed: Length of output: 223 🏁 Script executed: Length of output: 3592 🏁 Script executed: Length of output: 322 🏁 Script executed: Length of output: 146 🏁 Script executed: Length of output: 361 🏁 Script executed: Length of output: 1805
✅ Report without save - Reports this upgrade and asks again next update
✅ Report with save - Reports this upgrade and all future upgrades automatically
✅ Skip without save - Skips this time and asks again next update
✅ Skip with save - Never asks again
The key is the 🧠 Learnings used |


Simplified Upgrade Prompt Design
Per feedback, the prompt has been redesigned with a cleaner UX:
Changes
Benefits
Bug Fix
alwaysReportpreference across multiple upgradesScreenshot
Final upgrade prompt:

Testing
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.